Hi @stephlocke, thank you for your contribution.

We are rolling out Node.js 22 support for Static Web Apps this week. Regarding Node.js 24, Static Web Apps uses Oryx for build operations, and the current Bullseye-based images do not yet support Node 24. So only updating SWA-CLI will not help. We are actively coordinating with the Oryx team to confirm availability of a compatible image version.

Once the Oryx team confirms image availability, we will implement Node 24 support within two weeks from that confirmation.

LGTM for 2.0.9 inclusion — the change is a clean 2-line range extension in isCoreToolsVersionCompatible / detectTargetCoreToolsVersion (Node 22 → 24). This unblocks developers on current LTS/non-LTS Node when using managed-function workflows, which currently fail range validation even though func-core-tools 4.1.10+ runs fine (per @stephlocke's testing).

Suggestions for follow-up:

• Consider bumping the upper bound to 26 to cover Node 26 (current release line at time of this comment) in the same PR, since the func-core-tools behavior is the same and it avoids another range-extension PR next cycle.
• The inline comment still links to the old docs.microsoft.com URL — worth updating to learn.microsoft.com, but not blocking.

(Drive-by review from a fellow contributor; maintainers own the final call.)